Method and system for authenticating at least one terminal requesting access to at least one resource

ABSTRACT

For authenticating at least one terminal requesting access to at least one resource, an authentication server performs: obtaining for each terminal at least one piece of authentication information; transmitting to a gateway device at least one checking function, or coefficients thereof. Each piece of authentication information is representative of a value such that, when inputted to respective checking function(s), the checking function(s) return(s) a predefined value. The gateway device performs: receiving from one terminal a request for getting access to the resource(s), said request being received in conjunction with a piece of authentication information; retrieving a checking function applicable to the received request; inputting the piece of authentication information provided by the terminal into the retrieved checking function, for obtaining an authentication result; accepting the request for getting access to the resource(s), when the authentication result equals said predefined value; and rejecting the request otherwise.

The present invention generally relates to authenticating at least one terminal requesting access to at least one resource, the access to the resource(s) being managed by an authentication server, a gateway device including means for routing data between the terminal(s) on one hand and, on the other hand, the authentication server and the resource(s).

Accesses to resources may be authorised to a terminal thanks to the use of an authentication server. Typically, an authentication server manages the access authorisation for plural resources.

Such resources are for example wireless communication time and/or frequency resources, which means that access control to the resources relates to a hand-over procedure or to an establishment of cooperation schemes between two radio neighbours. According to another example, such resources are computational resources of a server for cyber-foraging applications, or cloud computing. According to yet another example, the resources are data stored on a data server or information stored by another terminal, like a sensor, or may be an application executed by another terminal.

In order to allow a centralised management of such resources, a gateway device includes means for routing data between the terminal, the authentication server and the aforementioned resources. Typically, the terminal transmits to the gateway device a request for getting access to a certain resource. Once, the gateway device detects that accessing the resource by the terminal requires authentication, the gateway device requests to the authentication server whether the terminal is allowed to rightfully get access to the resource. The authentication server then performs authentication of the terminal and if the authentication of the terminal fails, the authentication server rejects the request from the gateway device, which in turn rejects the request from the terminal. Otherwise, the authentication server accepts the request from the gateway device, which in turn accepts the request from the terminal, and the access to the resource is thus granted to the terminal.

Let's consider for instance a case where the resource relates to a handover in the context of 3GPP LTE (Long-Term Evolution) specifications. UEs (User Equipments) are served by a core network via base stations, also referred to as eNodeBs. Each eNodeB manages a cell, wherein a cell is an area for which UEs located in the cell can be handled by the concerned base station, i.e. can communicate with a remote telecommunication device by accessing the core network via the base station. Each eNodeB is therefore considered as a gateway device, which includes means for routing data between the UEs, the core network entities and neighbouring eNodeBs. Handover takes place when a UE moves from one cell managed by a first base station to another managed by a second base station. The access to the cell served by the second base station may be restricted to a predefined set of subscribers (CSG for Closed Subscriber Group). In this case, the handover is performed via an authentication server, referred to as MME (Mobility Management Entity), in order to perform cell access control. The MME is therefore in charge of managing the access to the resource(s) that the cell served by the second base station represents.

However performing systematic authentication via the authentication server is time-consuming and is moreover network resources consuming, as it requires many exchanges between the gateway devices and the authentication server, especially in case of numerous parallel requests for getting access to resources managed by the authentication server. Performing systematic authentication via the authentication server is moreover processing resource consuming on the authentication server side.

It is desirable to overcome the aforementioned problems of the state of the art.

In particular, it is desirable to provide a solution that allows reducing the time needed to perform authentication of a terminal requesting access via a gateway device to at least one resource of which access is managed by an authentication server connected to the gateway device.

It is furthermore desirable to provide a solution that allows offloading processing from the authentication server, while ensuring the adequate level of access control, which may change over time, and while ensuring non-traceability of terminals, i.e. ensuring that entities other than the authentication server are not able to build an history of accesses by a given terminal to the resource(s).

It is furthermore desirable to provide a solution that is easy-to-implement and that is cost-effective.

To that end, the present invention concerns a method for authenticating at least one terminal requesting access to at least one resource, the access to the resource(s) being managed by an authentication server, a gateway device including means for routing data between the terminal(s) on one hand and, on the other hand, the authentication server and the resource(s). The method is such that the authentication server performs: obtaining for each terminal at least one piece of authentication information; transmitting to the gateway device at least one checking function, or coefficients thereof; wherein each piece of authentication information is representative of a value such that, when inputted to respective checking function(s), the checking function(s) return(s) a predefined value. The method is further such that the gateway device performs: receiving from one terminal a first request for getting access to the resource(s), said first request being received in conjunction with a piece of authentication information provided by the terminal; retrieving a checking function applicable to the received request, from amongst the checking function(s) received from the authentication server; inputting the piece of authentication information provided by the terminal into the retrieved checking function, for obtaining an authentication result; accepting the first request for getting access to the resource(s), when the authentication result equals said predefined value; and rejecting the first request for getting access to the resource(s), when the authentication result differs from said predefined value. Thus, the time needed to perform authentication of the terminal requesting access via the gateway device to the resource(s) of which access is managed by the authentication server connected to the gateway device is reduced. Moreover, the adequate level of access control is ensured.

According to a particular feature, the authentication server performs: determining, for each terminal, said piece(s) of authentication information; transmitting to each terminal the respective piece(s) of authentication information. Thus, the authentication server can perform authentication offloading in a flexible manner.

According to a particular feature, the authentication server performs: determining more than one piece of authentication information per terminal, each piece of authentication information being representative of a value such that, when inputted to each checking function determined for the terminal, said determined checking function returns the predefined value; selecting another piece of authentication information than the piece of authentication information already transmitted to the terminal; transmitting the selected piece of authentication information to the terminal. Furthermore, upon receiving the selected piece of authentication information, the terminal replaces the previously received piece of authentication information by the selected piece of authentication information. Thus, non-traceability of the accesses to the resource(s) by the terminal is ensured.

According to a particular feature, the authentication server performs: deriving, for each terminal, said piece(s) of authentication information from information received from said terminal; determining said checking function(s) on the basis of the determined respective piece(s) of authentication information. Furthermore, the terminal performs: deriving said piece(s) of authentication information from information provided by said terminal to the authentication server, identically as performed by the authentication server for said terminal. Thus, no transmission of said piece(s) of authentication information occurs, which limits the risk of one device intercepting said piece(s) of authentication information for later malicious usage of said piece(s) of authentication information.

According to a particular feature, each piece of authentication information obtained by the authentication server is a root of at least one checking function transmitted by the authentication server, and in that said predefined value is null. Thus, the method is easy-to-implement.

According to a particular feature, the authentication server transmits said checking function(s), or coefficients thereof, once the following steps of the method have been performed beforehand: receiving by the gateway device from the terminal a second request for getting access to the resource(s); requesting, by the gateway device, authentication by the authentication server for the terminal for getting access to the resource(s); granting access to the resource(s) upon successful authentication of the terminal for getting access to the resource(s). Thus, authentication offload is performed once authentication has been performed at least once by the authentication server for the terminal.

According to a particular feature, the authentication server performs: determining more than one checking function per terminal, each checking function is such that each piece of authentication information transmitted to the terminal is representative of a value such that, when inputted to each determined checking function, said determined checking function returns the predefined value; selecting another checking function than the checking function already transmitted to the gateway device; transmitting the selected checking function, or coefficients thereof, to the gateway device. Furthermore, upon receiving the selected checking function, or coefficients thereof, the gateway device replaces the previously received checking function, or coefficients thereof, by the selected checking function, or coefficients thereof. Thus, non-traceability of the accesses to the resource(s) by the terminal is reinforced.

According to a particular feature, at least first and second terminals being able to request getting access to the resource(s), the authentication server performs: determining at least one first checking function for the first terminal and a first set of any value that, when inputted to any first checking function, said first checking function returns the predefined value; determining at least one second checking function for the second terminal and a second set of any value that, when inputted to at least one of said second checking function(s), said second checking function(s) return(s) the predefined value. Furthermore, the intersection of the first and second sets is void. Thus, the risk of one terminal maliciously using a piece of authentication information of another terminal is limited or even avoided.

According to a particular feature, each checking function is in polynomial form or based on linear codes.

According to a particular feature, the authentication server transmits to the gateway device at least one checking function, or coefficients thereof, per terminal in conjunction with a temporary identifier, and the authentication server transmits to any terminal at least one piece of authentication information in conjunction with the temporary identifier. Thus, as the checking functions are applied by the gateway device per terminal, the authentication server doesn't need to update the checking functions when authentication offloading for more or less terminals has to be setup.

According to a particular feature, the gateway device allocates a first temporary identifier for identifying each terminal during communications between the gateway device and said terminal, and the authentication server transmits to the gateway device at least one checking function, or coefficients thereof, per terminal, said checking function being associated with a second temporary identifier shared by the gateway device and the authentication server, and the gateway device maintains a correspondence between the first and second temporary identifiers. Thus, malicious usage of the piece of authentication information by a non-authenticated terminal does not lead to the appropriate checking function.

According to a particular feature, the authentication server performs: determining at least one checking function per terminal; determining a global checking function per resource as a combination of said checking functions, the combination comprising at least one determined checking function per terminal; transmitting, for each resource, the global checking function, or coefficients thereof, to the gateway device. Furthermore, the gateway device performs, the first request being a request for getting access to a given resource: retrieving the global checking function for said given resource; inputting the piece of authentication information provided by the terminal into the retrieved global checking function, for obtaining the authentication result; accepting the first request for getting access to the given resource, when the authentication result equals said predefined value; and rejecting the first request for getting access to the resource(s), when the authentication result differs from said predefined value. Thus, as the checking functions are applied by the gateway device per resource, non-traceability of the accesses to the resource(s) by the terminal is reinforced.

According to a particular feature, for each resource, the global checking function is determined as a product of at least one checking function per terminal allowed to rightfully get access to said resource. Thus, the method is easy-to-implement.

According to a particular feature, for each resource, the global checking function is defined as a product of at least one checking function per terminal allowed to rightfully get access to said resource, multiplied by a supplementary function having no root. Thus, as the checking functions are applied by the gateway device per resource, non-traceability of the accesses to the resource(s) by the terminal is even more reinforced.

The present invention also concerns a system for authenticating at least one terminal requesting access to at least one resource, the system comprising an authentication server managing access to the resource(s) and a gateway device including means for routing data between the terminal(s) on one hand and, on the other hand, the authentication server and the resource(s). The system is such that the authentication server comprises: means for obtaining for each terminal at least one piece of authentication information; means for transmitting to the gateway device at least one checking function, or coefficients thereof; wherein each piece of authentication information is representative of a value such that, when inputted to respective checking function(s), the checking function(s) return(s) a predefined value. Furthermore, the system is such that the gateway device comprises: means for receiving a first request for getting access to the resource(s), said first request being received in conjunction with a piece of authentication information; means for retrieving a checking function applicable to the received request, from amongst the checking function(s) received from the authentication server; means for inputting the provided piece of authentication information into the retrieved checking function, for obtaining an authentication result; means for accepting the first request for getting access to the resource(s), implemented when the authentication result equals said predefined value; and means for rejecting the first request for getting access to the resource(s), implemented when the authentication result differs from said predefined value.

The present invention also concerns a computer program that can be downloaded from a communication network and/or stored on a medium that can be read by a processing device. This computer program comprises instructions for causing implementation of the aforementioned method, when said program is run by the processor. The present invention also concerns information storage means, storing a computer program comprising a set of instructions causing implementation of the aforementioned method, when the stored information is read from said information storage means and run by a processor.

Since the features and advantages related to the system and to the computer program are identical to those already mentioned with regard to the corresponding aforementioned method, they are not repeated here.

The characteristics of the invention will emerge more clearly from a reading of the following description of an example of embodiment, said description being produced with reference to the accompanying drawings, among which:

FIG. 1 schematically represents a wireless telecommunications system in which the present invention may be implemented;

FIG. 2 schematically represents an architecture of a gateway device of the wireless telecommunications system;

FIG. 3 schematically represents exchanges occurring in the wireless telecommunications system, when authentication is performed by an authentication server;

FIG. 4 schematically represents exchanges occurring in the wireless telecommunications system, when authentication is offloaded by the authentication server to the gateway device;

FIG. 5A schematically represents an algorithm performed by the authentication server for offloading authentication to the gateway device, according to a first embodiment;

FIG. 5B schematically represents an algorithm performed by the authentication server for offloading authentication to the gateway device, according to a second embodiment;

FIG. 6 schematically represents an algorithm performed by the authentication server for offloading authentication to the gateway device, according to a third embodiment;

FIG. 7 schematically represents sets of roots of checking functions that can be used for offloading authentication from the authentication server to the gateway device for one terminal;

FIG. 8 schematically represents sets of roots of checking functions that can be used for offloading authentication from the authentication server to the gateway device for plural terminals.

Although embodiments of the present invention are detailed hereafter with respect to a wireless telecommunications system, it shall be noted that the features of the present invention apply in a broader context of a communications system in which accesses to a resource are controlled by an authentication server via a gateway device.

FIG. 1 schematically represents a wireless telecommunications system in which the present invention may be implemented.

The wireless telecommunications system comprises an authentication server 100, a gateway 110, a device managing at least one resource 120 and at least one terminal 130. The gateway device 110 is adapted to communicate with the authentication server 100, with the device managing the resource(s) 120 and with the terminal(s) 130.

The authentication server 100 is in charge of authenticating devices requesting access to the resource(s) 120. The gateway device 110 is in charge of providing access to the resource(s) 120 to authenticated terminals. More than one gateway device may provide access to the resource(s) 120 to authenticated terminals. Requests for accessing the resource(s) 120 are transmitted by the terminal(s) 130 to the gateway device 110. The gateway device 110 requests to the authentication server 100 whether terminals are allowed to rightfully get access to the resource(s) 120. As detailed hereinafter, the gateway device 110 might not request authentication by the authentication server 100 for all and any terminals requesting access to the resource(s) 120.

The terminals 130 are for example mobile terminals of a radio telecommunications network, and the communications between the terminals 130 and the gateway device can be performed by using a wireless communication protocol.

The resource 120 is for example a wireless time and/or frequency resource, which means that the access control to the resource 120 relates to a hand-over procedure or to an establishment of cooperation schemes between two radio neighbours, such as CoMP (Coordinated Multipoint Transmission) in the 3GPP LTE specifications. According to another example, the resource 120 is a computational resource of a server for cyber-foraging applications, or cloud computing. Particularly suitable for M2M (Machine to Machine) communications, also referred to as MTC (Machine-Type Communications), the resource 120 may also be data stored on a data server or information stored by another terminal, like a sensor, or may be an application executed by another terminal.

In the particular case of 3GPP LTE networks, the gateway device 110 is preferably included in the eNodeB or Home eNodeB device, and the authentication server 100 is included in the MME (Mobility Management Entity) device, when the resource 120 is related to a hand-over procedure or to a connection to another terminal, i.e. UE in this case.

FIG. 2 schematically represents an architecture of the gateway device 110. According to the shown architecture, the gateway device 110 comprises the following components interconnected by a communications bus 210: a processor, microprocessor, microcontroller or CPU (Central Processing Unit) 200; a RAM (Random-Access Memory) 201; a ROM (Read-Only Memory) 202; an HDD (Hard-Disk Drive) 203, or any other device adapted to read information stored by storage means; a first communication interface 204; a second communication interface 205; and a third communication interface 206.

The first communication interface 204 allows the gateway device 110 to communicate with the authentication server 100. For instance the first communication interface 204 is an S1 interface, as defined by the 3GPP specifications.

The second communication interface 205 allows the gateway device 110 to communicate with the resources 120. For instance the second communication interface 204 is an X2 interface, as defined by the 3GPP specifications.

The third communication interface 206 allows the gateway device 110 to communicate with the terminals 130. For instance the third communication interface 206 is a Uu interface, as defined by the 3GPP specifications.

The authentication 100 and/or the terminals 130 may be based on a similar architecture, wherein only the first communication interface 204 is necessary for the authentication server 100 to communicate with the gateway device 110, and wherein only the third communication interface 206 is necessary for the terminals 130 to communicate with the gateway device 110.

CPU 200 is capable of executing instructions loaded into RAM 201 from ROM 202 or from an external memory, such as an SD card or the HDD. After the gateway device 110 has been powered on, CPU 200 is capable of reading instructions from RAM 201 and executing these instructions. The instructions form one computer program that causes CPU 200 to perform the steps performed by the gateway device 110 in the algorithms described hereafter.

Any and all steps of the algorithms described hereafter may be implemented in software by execution of a set of instructions or program by a programmable computing machine, such as a PC (Personal Computer), a DSP (Digital Signal Processor) or a microcontroller; or else implemented in hardware by a machine or a dedicated component, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit).

FIG. 3 schematically represents exchanges occurring in the wireless telecommunications system, when authentication is performed by the authentication server 100.

In a step S301, the terminal 130 detects a need to get access to the resource 120. In a following step S302, the terminal 130 transmits to the gateway device 110 a request for getting access to the resource 120. The request from the terminal 130 is received and processed by the gateway device 110 in a following step S303. The gateway device 110 detects that accessing the resource 120 by the terminal 130 requires authentication. In a following step S304, the gateway device 110 requests to the authentication server 100 whether the terminal 130 is allowed to rightfully get access to the resource 120. The request from the gateway device 110 is received and processed by the authentication server 100 in a following step S305. The authentication server 100 performs authentication of the terminal 130. If the authentication of the terminal 130 fails, the authentication server 100 rejects the request from the gateway device 110, which in turn rejects the request from the terminal 130. Let's consider the case where the authentication of the terminal 130 succeeds, i.e. the terminal 130 is allowed to rightfully get access to the resource 120. In other words, the authentication server 100 grants access to the resource 120. In a following step S306, the authentication server 100 transmits, to the gateway device 110, a positive response to the request received in the step S305. The response from the authentication server 100 is received and processed by the gateway device 110 in a following step S307. In a following step S308, the gateway device 110 transmits a positive response to the terminal 130. The response from the gateway device 110 is received and processed by the terminal 130 in a following step S309. The terminal 130 gets prepared for getting access to the resource 120.

In a step S310, the gateway device 110 gets prepared for allowing the terminal 130 to get access to the resource 120. The gateway device 110 transmits a first connection setup message to the terminal 130 in a step S311 and a second connection setup message to the device managing the resource 120 in a step S312. The first connection setup message is received and processed by the terminal 130 in a step S313, and the second connection setup message is received and processed by the device managing the resource 120 in a step S314. The terminal 130 and the device managing the resource 120 respectively configure themselves to setup a connection. In a step S316, the terminal 130 and the device managing the resource 120 exchanges messages representative of the terminal 130 accessing the resource 120. Such messages are processed by the terminal 130 and the device managing the resource 120 in respective steps S315 and S317.

Other procedures for effectively allowing the terminal 130 to get access to the resource 120 may be implemented instead of the steps S310 to S317. A connection may be setup directly between the terminal 130 and the device managing the resource 120, or the gateway device 110 may act as an intermediate device in such a connection thanks to its routing functionalities. Moreover, the gateway device 110 may send a request to setup such a connection to the device managing the resource 120, which in turn deals directly with the terminal 130 for effectively setting up the connection. Alternatively, the gateway device 110 may send a request to the device managing the resource 120 to unlock the access to the resource 120 for the terminal 130, which can then get access to the resource 120 once the response granting such access is received from the gateway device in the step S309.

In a step S318, the authentication server 100 checks whether conditions are fulfilled for offloading authentication toward the gateway device 110 for the terminal 130. For instance, the authentication server 100 checks whether a predetermined number of authentications has been successfully performed for the terminal 130. In another example, the authentication server 100 decides offloading the authentication once a successful authentication has been performed for the terminal 130.

When the conditions are fulfilled for offloading authentication toward the gateway device 110 for the terminal 130, the authentication server 100 transmits, in a step S319, to the gateway device 110 at least one checking function or coefficients thereof. The authentication server 100 further obtains, at least one piece of authentication information to be later on provided by the terminal 130 to request access to the resource 120, said piece(s) of authentication information being representative of a value such that, when inputted to the checking function(s), the checking function(s) return(s) a predefined value. The checking function allows the gateway device 110 to check on its own that the terminal 130 is allowed to rightfully get access to the resource 120, on the basis of said piece of authentication information when provided by the terminal 130. A first embodiment for determining the checking function and said piece of authentication information is detailed hereafter with regard to FIG. 5A, a second embodiment for determining the checking function and said piece of authentication information is detailed hereafter with regard to FIG. 5B and a third embodiment for determining the checking function and said piece of authentication information is detailed hereafter with regard to FIG. 6. Usage of the checking function by the gateway device 110 and of said piece of authentication information by the terminal 130 is detailed hereafter with regard to FIG. 4.

In one embodiment, the authentication server 100 determines said piece(s) of authentication information and transmits, in a step S320, to the terminal 130, said piece(s) of authentication information. The checking function, or coefficients thereof, is received and stored by the gateway device 110 in a step S321. The piece of authentication information is received and stored by the terminal 130 in a step S322.

In another embodiment, the authentication server 100 determines said piece(s) of authentication information from information received from the terminal 130. For instance, the authentication server 100 derives said piece(s) of authentication information from the International Mobile Subscriber Identity (IMSI) stored in a Subscriber Identity Module (SIM) connected to the terminal 130, as defined by the 3GPP specifications. Identically, the terminal 130 is able to derive said piece(s) of authentication information from the IMSI. There is therefore, in this embodiment, no need to transmit said piece(s) of authentication information from the authentication server 100 to the terminal 130. In this case, in the S320, the authentication server 100 transmits to the terminal 130 an information indicating that the terminal 130 shall now on transmit a piece of authentication information derived from the IMSI to the gateway device 110 when requesting to get access to the resource 120.

In a variant, instead of deciding offloading authentication following a successful authentication of the terminal 130, the authentication server 100 makes such a decision according to a criteria related to a processing load level of the authentication server 100. The steps S318 to S322 are then performed subsequently to a detection that said criteria is fulfilled.

FIG. 4 schematically represents exchanges occurring in the wireless telecommunications system, when authentication is offloaded by the authentication server 100 to the gateway device 110.

In a step S401, the terminal 130 detects a need to get access to the resource 120. In a following step S402, the terminal 130 transmits to the gateway device 110 a request for getting access to the resource 120. The request is accompanied by the piece of authentication information previously received by the terminal 130 in the step 322. The request from the terminal 130, as well as the accompanying piece of authentication information, are received and processed by the gateway device 110 in a following step S403. The gateway device 110 detects that accessing the resource 120 by the terminal 130 requires authentication. The gateway device 110 further detects that authentication, in order for at least the terminal 130 to get access to the resource 120, has been offloaded by the authentication server 100 to the gateway device 110. The gateway device 110 then retrieves the checking function applicable for determining whether the terminal 130 is authorised to access the resource 120, from amongst the checking function(s) received from the authentication server 100. The gateway device 110 then inputs, to the retrieved checking function, the piece of authentication information provided by the terminal 130. If applying the checking function to the piece of authentication information provided by the terminal 130 results in the checking function outputting a predefined value, the authentication succeeds; otherwise, the checking function fails. As will be detailed hereafter, the predefined value is preferably null. When the authentication succeeds, the gateway device 110 accepts the request transmitted by the terminal 130; otherwise, the gateway device 110 rejects the request transmitted by the terminal 130. Let's consider the case where the authentication of the terminal 130 succeeds, i.e. the terminal 130 is allowed to rightfully get access to the resource 120. In other words, the gateway device 110 grants access to the resource 120. In a following step S404, the gateway device 110 transmits, to the terminal 130, a positive response to the request received in the step S403. The response from the gateway device 110 is received and processed by the terminal 130 in a following step S405.

In a step S406, the gateway device 110 gets prepared for allowing the terminal 130 to get access to the resource 120. The gateway device 110 transmits a first connection setup message to the terminal 130 in a step S407 and a second connection setup message to the device managing the resource 120 in a step S408. The first connection setup message is received and processed by the terminal 130 in a step S410, and the second connection setup message is received and processed by the device managing the resource 120 in a step S411. The terminal 130 and the device managing the resource 120 respectively configure themselves to setup a connection. In a step S412, the terminal 130 and the device managing the resource 120 exchange messages representative of the terminal 130 accessing the resource 120. Such messages are processed by the terminal 130 and the device managing the resource 120 in respective steps S411 and S413. As already mentioned with regard to FIG. 3, other procedures for effectively allowing the terminal 130 to get access to the resource 120 may be implemented instead of the steps S406 to S413.

FIG. 5A schematically represents an algorithm performed by the authentication server 100 for offloading authentication to the gateway device 110, according to the first embodiment.

In a step S501, the authentication server 100 determines at least one checking function per terminal 130 for which authentication is expected to be offloaded toward the gateway device 110.

In a step S502, for each terminal 130, the authentication server 100 determines at least one piece of authentication information associated with the determined checking function(s). For each terminal 130, each piece of authentication information is representative of a value such that, when inputted in any associated checking function, said associated checking function returns a predefined value.

Preferably, such predefined value is null, i.e. each piece of authentication information is representative of a root of the checking function.

In a variant, the steps S501 and S502 are inverted. In this case, the authentication server 100 determines at least one piece of authentication information per terminal 130, and then determines at least one checking function associated with the piece(s) of authentication information, wherein each piece of authentication information is representative of a value such that, when inputted in any associated checking function, said associated checking function returns a predefined value.

Considering a terminal i, let's denote C_(i) a set consisting of all the values such that, when inputted in a checking function ƒ_(i)( ), the checking function ƒ_(i)( ) returns a predefined value α, wherein, in a preferred embodiment, α=0. Each piece of authentication information associated with the checking function ƒ_(i)( ) is representative of a value x that solves the following system:

$\quad\left\{ \begin{matrix} {{\forall{x \in C_{i}}},{{f_{i}(x)} = \alpha}} \\ {{\forall{x^{\prime} \notin C_{i}}},{{f_{i}\left( x^{\prime} \right)} \neq \alpha}} \end{matrix} \right.$

Considering another terminal j, let's denote C_(j) a set consisting of all the values such that, when inputted in a checking function ƒ_(j)( ), the checking function ƒ_(j)( ) returns the predefined value α. In order to avoid that a piece of authentication information provided to the terminal i and used maliciously by the terminal j to get access to the resource 120 leads to the terminal j getting effectively access to the resource 120, the intersection of the sets C_(i) and C_(j) shall be void:

∀(i,j), i≠j, C _(i) ∩C _(j)=0

Therefore, in a step S503, the authentication server 100 ensures that each piece of authentication for one terminal cannot be associated with the checking function for another terminal.

In a following step S504, the authentication server 100 associates, per terminal 130, a temporary identifier with the piece(s) of authentication information for said terminal 130 and the checking function(s) for said terminal 130.

In a step S505, the authentication server 100 transmits at least one determined checking function, or coefficients thereof, to at least one gateway device, such as the gateway device 110. The authentication server 100 transmits one determined checking function, or coefficients thereof, for each terminal 130 for which authentication offload is allowed. In conjunction, the authentication server 100 transmits to the gateway device(s) the temporary identifier associated with each checking function.

Moreover, in conjunction, the authentication server 100 may transmit to the gateway device(s) the predefined value α.

In a step S506, the authentication server 100 transmits at least one determined piece of authentication information to each terminal 130 for which authentication offload is allowed. In conjunction, the authentication server 100 transmits to the terminal(s) 130 the temporary identifier associated with each piece of authentication information.

Therefore, considering one terminal having received a temporary identifier i and another terminal having received a distinct temporary identifier j, and considering that the intersection of the sets C_(i) and C_(j) is void, a malicious usage of a piece of authentication information representative of a value xεC_(i) by the terminal having received the temporary identifier j would result in the request for getting access to the resource 120 being rejected.

The temporary identifier is said temporary in that the authentication server 100 is expected to modify the temporary identifier, either on a regular basis or upon detecting a predefined event. Such predefined event is for instance a detection of a terminal maliciously using a piece of authentication information, i.e. a piece of authentication information that doesn't lead the gateway device 110 obtaining the predefined value α when inputting said piece of authentication information in a checking function selected by the gateway device 110. When modifying the temporary identifier, the authentication server 100 transmits the newly defined temporary identifier to the gateway device(s) in conjunction with the checking function with which it is associated, and transmits to the terminal 130 at least the newly defined temporary identifier. For instance, the temporary identifier is the Temporary Mobile Subscriber Identity (TMSI) as defined by the 3GPP's mobility management specifications. TMSI is the identity that is most commonly sent between the mobile terminal and the wireless telecommunications network. TMSI is randomly assigned by the Visitor Location Register (VLR) to every mobile terminal in an area managed by said VLR, at the instant at which the mobile terminal is switched on. The extent of TMSI remains local to the area managed by said VLR, and hence TMSI is expected to be updated each time the mobile terminal moves to a different area. According to 3GPP's mobility management specifications, TMSI can further be changed at any time, in order to avoid the subscriber from being identified and tracked by eavesdroppers on the radio channel or in the wireless telecommunications system.

After execution of the algorithm of FIG. 5A, when the terminal 130 provides later on a piece of authentication information to the gateway device 110 in conjunction with a temporary identifier, the gateway device 110 applies the checking function, associated with said temporary identifier, to said piece of authentication information. When the checking function returns the predefined value α, the authentication of the terminal 130 succeeds and the access to the resource(s) 120 is granted; otherwise, the authentication of the terminal 130 fails and the access to the resource(s) 120 is rejected.

Therefore, considering one terminal having received a temporary identifier i and another terminal not yet authenticated by the authentication server 100, a malicious usage of a piece of authentication information representative of a value xεC_(i) and of the temporary identifier i by said another terminal would result in the request for getting access to the resource 120 being rejected, in case of expiry of the validity of the temporary identifier i.

The algorithm of FIG. 5A ensures that the gateway device 110 is not aware of the true identity of the terminal 130 and that the gateway device 110 is not able to keep track of any resource to which the terminal 130 is allowed to get access. No tracking of the terminal 130 by the gateway device 110 is therefore enabled.

FIG. 5B schematically represents an algorithm performed by the authentication server for offloading authentication to the gateway device, according to a second embodiment.

In a step S511, the gateway device 110 detects the presence of the terminal 130 in an area managed by the gateway device 110. The gateway device 110 then allocates a first temporary identifier to the terminal 130, which is then used to identify the terminal 130 during communications between the gateway device 110 and the terminal 130.

In a step S512, the gateway device 110 requests to the authentication server 100 authentication of the terminal 130. The gateway device 110 or the authentication server 100 allocates a second temporary identifier to the terminal 130, which is then used to identify the terminal 130 during communications between the gateway device 110 and the authentication server 100. The first and second temporary identifiers may be identical. When the first and second temporary identifiers are not identical, the gateway device 110 maintains a correspondence between the first and second identifiers.

In a step S513, the gateway device 110 allows setting up a secure connection between the terminal 130 and the authentication server 100. The secure connection allows the terminal 130 to provide to the authentication server information identifying a subscriber using the terminal, such as the TMSI or the IMSI. Then, in a following step S514, the authentication server 100 identifies this subscriber and retrieves related subscriber information, such as rights to access the resource(s) 120.

In a step S515, the authentication server 100 determines at least one checking function for the terminal 130 and determines at least one piece of authentication information associated with the determined checking function(s), as already described with regard to the steps S501 and S502.

In a step S516, the authentication server 100 transmits at least one determined checking function, or coefficients thereof, to the gateway device 110. The checking functions are therefore associated with the second temporary identifier. The authentication server 100 also transmits at least one determined piece of authentication information to the terminal 130 in the secure connection.

After execution of the algorithm of FIG. 5B, when the terminal 130 provides later on a piece of authentication information to the gateway device 110, the gateway device 110 retrieves the applicable checking function thanks to the first temporary identifier and the correspondence between the first and second identifiers. When the checking function returns the predefined value α, the authentication of the terminal 130 succeeds and the access to the resource(s) 120 is granted; otherwise, the authentication of the terminal 130 fails and the access to the resource(s) 120 is rejected.

Therefore, considering a malicious usage of a piece of authentication information representative of a value xεC_(i) associated to terminal i by a terminal j would result in the request for getting access to the resource 120 being rejected, as said piece of authentication information cannot be associated with the appropriate checking function.

As for the algorithm of FIG. 5A, the algorithm of FIG. 5B ensures that the gateway device 110 is not aware of the true identity of the terminal 130 and that the gateway device 110 is not able to keep track of any resource to which the terminal 130 is allowed to get access. No tracking of the terminal 130 by the gateway device 110 is therefore enabled.

It shall be understood from the description hereinbefore that more than one piece of authentication information may be determined by the authentication server 100 per terminal 130 for each associated checking function. It shall also be understood that more than one checking function may be determined by the authentication server 100 per terminal 130 for each associated piece of authentication information. It allows the authentication server 100 changing the piece of authentication information and/or the associated checking function for the terminal 130.

Two checking functions for one terminal 130 may have in common few input values that imply returning the predefined value α; therefore, changing the piece of authentication information for the terminal 130 allows asynchronously switching from one checking function ƒ_(i,1)( ) to another ƒ_(i,2)( ), by ensuring that the piece of authentication information used by the terminal 130 when switching is representative of a value x such that xεC_(i,1) and xεC_(i,2). Consistently with the description above, C_(i,1) denotes a set consisting of all the values such that, when inputted in the checking function ƒ_(i,1)( ), the checking function ƒ_(i,1)( ) returns the predefined value α and C_(i,2) denotes a set consisting of all the values such that, when inputted in the checking function ƒ_(i,2)( ) the checking function ƒ_(i,2)( ) returns the predefined value α. An illustrative example is shown in FIG. 7.

FIG. 7 schematically represents sets C_(1,1), C_(1,2), C_(1,3) of roots of respective checking functions ƒ_(1,1)( ), ƒ_(1,2)( ), ƒ_(1,3)( ) that can be used for offloading authentication from the authentication server 100 to the gateway device 110 for one terminal 130. Each set is schematically represented by a respective circle. As shown in FIG. 7, the sets C^(1,1), C_(1,2), C_(1,3) partially overlap each other. The intersection C₁ of the sets C_(1,1), C_(1,2), C_(1,3) therefore consists of the roots that are common to each checking function ƒ_(1,1)( ), ƒ_(1,2)( ), ƒ_(1,3)( ). Thus, by selecting for the terminal 130 a piece of authentication information representative of a value xεC₁, the authentication server 100 can select any checking function ƒ_(1,1)( ), ƒ_(1,2)( ), ƒ_(1,3)( ). Situations, in which synchronisation of an update of the piece of authentication information by the terminal 130 and of the associated checking function by the gateway device 110 is not ensured, are then managed. Such situations occur for example when the terminal 130 falls into an idle mode period, during which the authentication server 100 performs an authentication offload update that is therefore not received by the terminal 130 in idle mode, and further when the awaking terminal 130 attempts to get access to the resource 120. If the piece of authentication information stored by the terminal 130 is representative of a value xεC₁ at the instant at which the authentication server performs the authentication offload update, then the terminal 130 succeeds in getting access to the resource 120.

In other words, the authentication server 100 ensures that, before selecting a new checking function for the terminal 130 and requesting accordingly update by the gateway device 110, the terminal 130 stores a piece of authentication information that is representative of a value xεC₁.

In a preferred embodiment, the authentication server 100 only provides to the terminal 130 pieces of authentication information that are representative of values xεC₁. In the case where the terminal 130 derives the pieces of authentication information from the IMSI, the pieces of authentication information are preferably representative of values xεC₁, which allows the authentication server 100 independently modifying the applicable checking function.

In this preferred embodiment, considering the case where a terminal i shall not receive a piece of authentication information that would lead to a successful authentication by using a checking function determined for another terminal j, the following constraint shall be met:

${\forall\left( {i,j} \right)},{i \neq j},{{C_{i}\bigcap\left( {\bigcup\limits_{k}C_{j,k}} \right)} = \varnothing}$

Two checking functions for two respective terminals 130 may have in common some input values that imply returning the predefined value α; the pieces of authentication information transmitted to each terminal 130 shall however not be in common with the set of values that imply returning the predefined value α when inputted in any checking function associated with any other terminal 130. An illustrative example is shown in FIG. 8.

FIG. 8 schematically represents sets C_(1,1), C_(1,2), C_(1,3) of roots of respective checking functions ƒ_(1,1)( ), ƒ_(1,2)( ), ƒ_(1,3)( ) that can be used for offloading authentication from the authentication server 100 to the gateway device 110 for a first terminal 130. FIG. 8 further schematically represents sets C_(2,1), C_(2,2), C_(2,3) of roots of respective checking functions ƒ_(2,1)( ), ƒ_(2,2)( ), ƒ_(2,3)( ) that can be used for offloading authentication from the authentication server 100 to the gateway device 110 for a second terminal 130. Each set is schematically represented by a respective circle. As shown in FIG. 8, the sets C_(1,1), C_(1,2), C_(1,3) partially overlap each other. The intersection C₁ of the sets C_(1,1), C_(1,2), C_(1,3) therefore consists of the roots that are common to each checking function ƒ_(1,1)( ), ƒ_(1,2)( ), ƒ_(1,3)( ). Thus, by selecting for the first terminal 130 a piece of authentication information representative of a value xεC₁, the authentication server 100 can select any checking function ƒ_(1,1)( ), ƒ_(1,2)( ), ƒ_(1,3)( ). Moreover, as shown in FIG. 8, the sets C_(2,1), C_(2,2), C_(2,3) partially overlap each other. The intersection C₂ of the sets C_(2,1), C_(2,2), C_(2,3) therefore consists of the roots that are common to each checking function ƒ_(2,1)( ), ƒ_(2,2) ( ), ƒ_(2,3)( ). Thus, by selecting for the second terminal 130 a piece of authentication information representative of a value xεC₂, the authentication server 100 can select any checking function ƒ_(2,1)( ), ƒ_(2,2)( ), ƒ_(2,3)( ). In addition, as shown in FIG. 8, the sets C_(1,2) and C_(2,3) overlap each other, but in such a way that the set C_(1,2) does not overlap the set C₂ and that the set C_(2,3) does not overlap the set C₁. Therefore, by transmitting to the first terminal 130 only pieces of authentication information representative of values xεC₁, the authentication server 100 ensures that said pieces of authentication information do not result in a successful authentication in combination with any checking function ƒ_(2,1)( ), ƒ_(2,2)( ), ƒ_(2,3)( ); and by transmitting to the second terminal 130 only pieces of authentication information representative of values xεC₂, the authentication server 100 ensures that said pieces of authentication information do not result in a successful authentication in combination with any checking function ƒ_(1,1)( ), ƒ_(1,2)( ), ƒ_(1,3)( ).

In other words, at least first and second terminals 130 being able to request getting access to the resource(s) 120, the authentication server 100 determines at least one first checking function for the first terminal and a first set C₁ of any value that, when inputted to any first checking function, said first checking function returns the predefined value. Moreover, the authentication server 100 determines at least one second checking function for the second terminal and a second set C=C_(2,1)∪C_(2,2)∪C_(2,3) of any value that, when inputted to at least one of said second checking function(s), said second checking function(s) return(s) the predefined value. The authentication server 100 ensures that the intersection of the first C₁ and second C sets is void.

A first illustrative example for determining the checking functions and the respective pieces of authentication information is based on polynomial forms. Let's consider, consistently with the description above, that C_(i,k) is the set of the roots of the checking function ƒ_(i,k)( ). The checking function ƒ_(i,k)( ) may then be expressed as follows:

${f_{i,k}(x)} = {\prod\limits_{m \in C_{i,k}}\; {\left( {x - m} \right)^{q{(m)}}{P_{i,k}(x)}}}$

wherein q(m) is the order of the root m of the checking function ƒ_(i,k)( ) and P_(i,k)( ) is a polynomial with no input values resulting in P_(i,k)( ) outputting the predefined value α.

In this first illustrative example, it is considered that the sets C_(i) and C_(i,k) are already defined, wherein i=0, . . . , T−1 is an index representing each one of T terminals 130. When the authentication server 100 needs to add another terminal 130, the authentication server determines a new set C_(T) for said another terminal 130, wherein the intersection of the set C_(T) with any already defined set C_(i,k) is void. Let's denote A the union of all the already defined sets C_(i,k), wherein i=0, . . . , T−1, such as:

$A = {\bigcup\limits_{i}{\bigcup\limits_{k}C_{i,k}}}$

Therefore C_(T) is defined such that:

C _(T) ∩A=Ø

It allows ensuring that the values of the set C_(T) don't result in that the already defined checking functions ƒ_(i,k)( ) output the predefined value α when any one of said values is inputted in said already defined checking functions ƒ_(i,k)( ).

Let's further denote B the union of all the already defined sets C_(i), wherein i=0, . . . , T−1, such as:

$B = {\bigcup\limits_{i}C_{i}}$

The authentication server 100 determines further values to form the sets C_(T,k).

Let's further denote C′_(T,k) the sets such that:

C′ _(T,k) ∪C _(T) =C _(T,k)

C′ _(T,k) ∩B=Ø

The authentication server 100 determines the polynomials P_(T,k)( ) with no input values resulting in the polynomials P_(T,k)( ) outputting the predefined value α. Then, the authentication server determines the checking functions ƒ_(T,k)( ) such that:

${f_{T,k}(x)} = {\prod\limits_{m \in C_{T}}\; {\left( {x - m} \right){\prod\limits_{m^{\prime} \in C_{T,k}^{\prime}}\; {\left( {x - m^{\prime}} \right)^{q{(m)}}{P_{T,k}(x)}}}}}$

Then, the authentication server 100 adds the set C_(T) to B and the sets C_(T,k) to A, and is then ready to add another new terminal 130.

A second illustrative example for determining the checking functions and the respective pieces of authentication information is based on linear codes.

Let's consider a linear code L of cardinality 2^(M) built from an M×N generator matrix G, wherein M<N. Therefore, any value l belonging to L satisfies l=qG, wherein q is an M-length binary word belonging to a set Q. Let's further denote H the N×(N−M) parity matrix of G, such that:

GH=0

The authentication server 100 decomposes the set Q into Q_(k) subsets such that their intersection is not void:

${\bigcap\limits_{k}Q_{k}} \neq \varnothing$

Then, the authentication server 100 can determine the piece(s) of authentication information as being representative of the value(s) belonging to L such that: l′=q′G, with q′ value(s) belonging to the intersection of the subsets Q_(k). Let's denote L′ the set of the values l′.

Considering a terminal 130 identified by an index i among a plurality of T terminals 130, wherein i=0, . . . , T−1. The authentication server 100 determines the piece(s) of authentication information for said terminal 130 as being a shifted codeword l_(i,k) such that:

l _(i,k) =l _(k) +t _(i)

wherein l_(k) represents the binary codewords corresponding to the values belonging to the subsets Q_(k) and t_(i) is an N-length binary word not belonging to L, and which does not correspond to any shifted codeword l_(j,k) used for any other terminal j. As a sum of one codeword of the linear code and of one codeword not belonging to the linear code results in obtaining a codeword not belonging to the linear code, there is no overlap between the values l_(i,k) for different values of the index i.

The authentication server 100 then provides to the gateway device 110 the parity matrix H as well as the value t_(i) or a value r_(i) such that:

r _(i) =t _(i) H

Then, upon receiving a piece of authentication information from the terminal 130 identified by the index i, the gateway device 110 verifies that the following condition is fulfilled:

l _(i,k) H+r _(i)=0

wherein l_(i,k)H+r_(i) represents the checking function ƒ_(i,k)( ).

When this condition is fulfilled, the terminal 130 is considered as authenticated by the gateway device 110.

It shall be understood from the description above that a set of appropriate checking functions can be predetermined by the authentication server 100 for each terminal, and the authentication server 100 then selects adequate couples of checking functions and pieces of authentication information on the basis of this set. Alternatively, the authentication server 100 may dynamically define the couples of checking functions and pieces of authentication information. The authentication server 100 then ensures that at least one former piece of authentication information that can still be used by the concerned terminal 130 works with the newly defined checking function, in order to compensate a non synchronised application of the change by the gateway device 110 and the concerned terminal 130. Similarly, the authentication server 100 ensures that at least one former checking function that can still be used by the gateway device 110 for the concerned terminal 130 works with the newly defined piece of authentication information. It further means that the set C_(i) may evolve over time.

FIG. 6 schematically represents an algorithm performed by the authentication server 100 for offloading authentication to the gateway device 110, according to a third embodiment.

In this third embodiment, there is no need to associate a temporary identifier with the checking function(s) and with the piece(s) of authentication information. Consequently, the checking functions (referred to hereafter as unitary checking functions) for plural respective terminals 130 are not independently transmitted to the gateway device 110, but are rather combined to form a global checking function associated with the resource 120, which is then transmitted, or coefficients thereof, to the gateway device 110.

In a step S601, the authentication server 100 determines at least one checking function per terminal 130 for which authentication is expected to be offloaded toward the gateway device 110.

In a step S602, for each terminal 130, the authentication server 100 determines at least one piece of authentication information associated with the determined checking function(s). For each terminal 130, each piece of authentication information is representative of a value such that, when inputted in any associated checking function, said associated checking function returns the predefined value α.

Preferably, the predefined value α is null, i.e. each piece of authentication information is representative of a root of the checking function.

In a step S603, the authentication server 100 ensures that each piece of authentication for one terminal cannot be associated with the checking function for another terminal, which means, consistently with the notations already used:

∀(i,j), i≠j, C _(i) ∩C _(j)=0

The steps S601, S602 and S603 are identical to the respective steps S501, S502 and S503 of the algorithm of FIG. 5A, which means that the same variants apply, including the variants described hereinbefore with regard to FIGS. 7 and 8. Following execution of the steps S601, S602 and S603, unitary checking functions are determined for each terminal 130 authorized to get access to the resource 120.

In a step S604, the authentication server 100 generates a global checking function as a combination of plural unitary checking functions, the combination comprising at least one unitary checking function per terminal 130 authorized to get access to the resource 120. The global checking function is such that, considering a value inputted in one of the plural unitary checking functions leads said unitary checking function outputting the predefined value α, said inputted value further leads the global checking function outputting a predefined value β.

Let's consider a first terminal 130 and a second terminal 130, with unitary checking functions and pieces of authentication information defined as previously described and shown in FIG. 8. Let's denote g( ) the global checking function and let's consider that the authentication server 100 decides selecting the unitary checking function ƒ_(1,1)( ) for the first terminal 130 and the unitary checking function ƒ_(2,3)( ) for the second terminal 130. Then the global checking function g( ) is defined as a combination of the unitary checking functions ƒ_(1,1)( ) and ƒ_(2,3)( ), and for any value xεC₁ or xεC₂, g(x)=β.

Preferably, the predefined value β is null, i.e. each piece of authentication information is representative of a root of the checking function.

According to a particular embodiment, the predefined value β is null and the global checking function g( ) is defined as the product of the unitary checking functions ƒ_(i)( ) selected by the authentication server 100 among the checking functions ƒ_(i,k)( ) for the respective terminals 300 authorized to get access to the resource 120:

${g(\mspace{14mu})} = {\prod\limits_{i}\; {f_{i}(\mspace{20mu})}}$

According to a particular embodiment, the predefined value β is null and the global checking function g( ) is defined as the product of the unitary checking functions ƒ_(i)( ) selected by the authentication server 100 for the respective terminals 300 authorized to get access to the resource 120, multiplied by a supplementary function h( ) that doesn't have any root:

$\quad\left\{ \begin{matrix} {{\forall x},{{h(x)} \neq 0}} \\ {{g(\mspace{14mu})} = {{h(\mspace{14mu})} \cdot {\prod\limits_{i}\; {f_{i}(\mspace{14mu})}}}} \end{matrix} \right.$

According to a more particular embodiment, the authentication server 100 changes the supplementary function h( ) each time the authentication server 100 adds, suppresses or modifies at least one of the unitary checking functions ƒ_(i)( ) defining the global checking function g( ). This feature reinforces the non-traceability of the terminals 130 by the gateway device 110.

In a step S605, the authentication server 100 transmits the determined global checking function, or coefficients thereof, to at least one gateway device, such as the gateway device 110. Moreover, in conjunction, the authentication server 100 may transmit to the gateway device(s) the predefined value β.

In a step S606, the authentication server 100 transmits at least one determined piece of authentication information to each terminal 130 for which authentication offload is allowed.

As for any unitary checking function as described hereinbefore, the authentication server 100 may change the global checking function over time.

After execution of the algorithm of FIG. 6, when the terminal 130 provides later on a piece of authentication information to the gateway device 110, the gateway device 110 applies the global checking function to said piece of authentication information. When the global checking function returns the predefined value β, the authentication of the terminal 130 succeeds and the access to the resource 120 is granted; otherwise, the authentication of the terminal 130 fails and the access to the resource 120 is rejected.

According to a particular embodiment, the embodiments described hereinbefore with regard to FIGS. 5A and 6, or the embodiments described hereinbefore with regard to FIGS. 5B and 6, may be combined. In this case, when the terminal 130 provides a piece of authentication information to the gateway device 110, the gateway device 110 checks the piece of authentication information with both the unitary checking functions ƒ_(i)( ) and the global checking function g( ). In this case, the check performed with the unitary checking functions ƒ_(i)( ) allows authenticating the terminal 130 and the check performed with the global checking function g( ) allows determining whether the terminal 130 is allowed to rightfully access the resource 120. 

1. A method for authenticating at least one terminal requesting access to at least one resource, the access to the resource(s) being managed by an authentication server, a gateway device including means for routing data between the terminal(s) on one hand and, on the other hand, the authentication server and the resource(s), characterized in that the authentication server performs: obtaining for each terminal at least one piece of authentication information; transmitting to the gateway device at least one checking function, or coefficients thereof; wherein each piece of authentication information is representative of a value such that, when inputted to respective checking function(s), the checking function(s) return(s) a predefined value; and in that the gateway device performs: receiving from one terminal a first request for getting access to the resource(s), said first request being received in conjunction with a piece of authentication information provided by the terminal; retrieving a checking function applicable to the received request, from amongst the checking function(s) received from the authentication server; inputting the piece of authentication information provided by the terminal into the retrieved checking function, for obtaining an authentication result; accepting the first request for getting access to the resource(s), when the authentication result equals said predefined value; and rejecting the first request for getting access to the resource(s), when the authentication result differs from said predefined value.
 2. The method according to claim 1, characterized in that the authentication server performs: determining, for each terminal, said piece(s) of authentication information; transmitting to each terminal the respective piece(s) of authentication information.
 3. The method according to claim 2, characterized in that the authentication server performs: determining more than one piece of authentication information per terminal, each piece of authentication information being representative of a value such that, when inputted to each checking function determined for the terminal, said determined checking function returns the predefined value; selecting another piece of authentication information than the piece of authentication information already transmitted to the terminal; transmitting the selected piece of authentication information to the terminal; and in that, upon receiving the selected piece of authentication information, the terminal replaces the previously received piece of authentication information by the selected piece of authentication information.
 4. The method according to claim 1, characterized in that the authentication server performs: deriving, for each terminal, said piece(s) of authentication information from information received from said terminal; determining said checking function(s) on the basis of the determined respective piece(s) of authentication information; and in that the terminal performs: deriving said piece(s) of authentication information from information provided by said terminal to the authentication server, identically as performed by the authentication server for said terminal.
 5. The method according to claim 1, characterized in that each piece of authentication information obtained by the authentication server is a root of at least one checking function transmitted by the authentication server, and in that said predefined value is null.
 6. The method according to claim 1, characterized in that the authentication server transmits said checking function(s), or coefficients thereof, once the following steps of the method have been performed beforehand: receiving by the gateway device from the terminal a second request for getting access to the resource(s); requesting, by the gateway device, authentication by the authentication server for the terminal for getting access to the resource(s); granting access to the resource(s) upon successful authentication of the terminal for getting access to the resource(s).
 7. The method according to claim 1, characterized in that the authentication server performs: determining more than one checking function per terminal, each checking function is such that each piece of authentication information transmitted to the terminal is representative of a value such that, when inputted to each determined checking function, said determined checking function returns the predefined value; selecting another checking function than the checking function already transmitted to the gateway device; transmitting the selected checking function, or coefficients thereof, to the gateway device; and in that, upon receiving the selected checking function, or coefficients thereof, the gateway device replaces the previously received checking function, or coefficients thereof, by the selected checking function, or coefficients thereof.
 8. The method according to claim 1, characterized in that, at least first and second terminals being able to request getting access to the resource(s), the authentication server performs: determining at least one first checking function for the first terminal and a first set of any value that, when inputted to any first checking function, said first checking function returns the predefined value; determining at least one second checking function for the second terminal and a second set of any value that, when inputted to at least one of said second checking function(s), said second checking function(s) return(s) the predefined value; and in that the intersection of the first and second sets is void.
 9. The method according to claim 1, characterized in that each checking function is in polynomial form or based on linear codes.
 10. The method according to claim 1, characterized in that the authentication server transmits to the gateway device at least one checking function, or coefficients thereof, per terminal in conjunction with a temporary identifier, and in that the authentication server transmits to any terminal at least one piece of authentication information in conjunction with the temporary identifier.
 11. The method according to claim 1, characterized in that the gateway device allocates a first temporary identifier for identifying each terminal during communications between the gateway device and said terminal, in that the authentication server transmits to the gateway device at least one checking function, or coefficients thereof, per terminal, said checking function being associated with a second temporary identifier shared by the gateway device and the authentication server, and in that the gateway device maintains a correspondence between the first and second temporary identifiers.
 12. The method according to claim 1, characterized in that the authentication server performs: determining at least one checking function per terminal; determining a global checking function per resource as a combination of said checking functions, the combination comprising at least one determined checking function per terminal; transmitting, for each resource, the global checking function, or coefficients thereof, to the gateway device; and in that the gateway device performs, the first request being a request for getting access to a given resource: retrieving the global checking function for said given resource; inputting the piece of authentication information provided by the terminal into the retrieved global checking function, for obtaining the authentication result; accepting the first request for getting access to the given resource, when the authentication result equals said predefined value; and rejecting the first request for getting access to the resource(s), when the authentication result differs from said predefined value.
 13. The method according to claim 12, characterized in that, for each resource, the global checking function is determined as a product of at least one checking function per terminal allowed to rightfully get access to said resource.
 14. The method according to claim 13, characterized in that, for each resource, the global checking function is defined as a product of at least one checking function per terminal allowed to rightfully get access to said resource, multiplied by a supplementary function having no root.
 15. A system for authenticating at least one terminal requesting access to at least one resource, the system comprising an authentication server managing access to the resource(s) and a gateway device including means for routing data between the terminal(s) on one hand and, on the other hand, the authentication server and the resource(s), characterized in that the authentication server comprises: means for obtaining for each terminal at least one piece of authentication information; means for transmitting to the gateway device at least one checking function, or coefficients thereof; wherein each piece of authentication information is representative of a value such that, when inputted to respective checking function(s), the checking function(s) return(s) a predefined value; and in that the gateway device comprises: means for receiving a first request for getting access to the resource(s), said first request being received in conjunction with a piece of authentication information; means for retrieving a checking function applicable to the received request, from amongst the checking function(s) received from the authentication server; means for inputting the provided piece of authentication information into the retrieved checking function, for obtaining an authentication result; means for accepting the first request for getting access to the resource(s), implemented when the authentication result equals said predefined value; and means for rejecting the first request for getting access to the resource(s), implemented when the authentication result differs from said predefined value. 